src/hooks/useGitHubData.ts (1)

104-115: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Empty-search transitions do not cancel the active request.

The new abort path only runs after the !username.trim() / rateLimited guard. When Tracker.tsx clears the debounced username and suppresses the next fetch, the previous controller stays active, so that stale response can still pass the requestId/controller checks and repopulate state after the input is blank. Abort the current controller before this guard, or expose an explicit cancel/reset path for empty searches.

Suggested minimal fix

-      if (!octokit || !username.trim() || rateLimited) {
-        return;
-      }
-
-      // Cancel any active in-flight request before triggering a new one
       if (abortControllerRef.current) {
         abortControllerRef.current.abort();
       }
+
+      if (!octokit || !username.trim() || rateLimited) {
+        return;
+      }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/hooks/useGitHubData.ts` around lines 104 - 115, The guard in
useGitHubData currently returns before aborting an in-flight request, so
clearing the debounced username can leave a previous request active; move or
duplicate the abort logic so abortControllerRef.current?.abort() runs before the
early-return (i.e., before checking !username.trim() || rateLimited), or add an
explicit cancel/reset path that calls abortControllerRef.current.abort(), clears
abortControllerRef.current, and increments/invalidates requestId when username
becomes empty; update references to abortControllerRef and requestId in the hook
(where controller is created and assigned) to ensure stale responses cannot
repopulate state after an empty search.